Methods and apparatus to verify and/or correct media lineup information

ABSTRACT

Methods and apparatus to verify and/or correct media lineup information are disclosed. Disclosed example apparatus include a comparator to compare media presentation data representative of media output by a set top box to reference data corresponding to a first station to determine whether the media presentation data corresponds to the reference data, the media presentation data collected while the set top box was tuned to a first channel number. The comparator is also to determine a second station that corresponds to the media presentation data when the media presentation data does not correspond to the reference data, and relate the first channel number to the second station to create a second channel map to replace a first channel map that related the first channel number to the first station based on channel lineup information for the set top box.

RELATED APPLICATION

This patent arises from a continuation of U.S. patent application Ser.No. 15/206,991, entitled “METHODS AND APPARATUS TO VERIFY AND/OR CORRECTMEDIA LINEUP INFORMATION,” filed on Jul. 11, 2016, which is acontinuation of U.S. patent application Ser. No. 14/473,639, entitled“METHODS AND APPARATUS TO VERIFY AND/OR CORRECT MEDIA LINEUPINFORMATION,” filed on Aug. 29, 2014, which claims priority to U.S.Provisional Patent Application No. 61/918,513, filed Dec. 19, 2013.Priority to U.S. patent application Ser. No. 15/206,991, U.S. patentapplication Ser. No. 14/476,639, and U.S. Provisional Patent ApplicationNo. 61/918,513 is claimed. U.S. patent application Ser. No. 15/206,991,U.S. patent application Ser. No. 14/476,639, and U.S. Provisional PatentApplication No. 61/918,513 are incorporated herein by reference in theirrespective entireties.

FIELD OF THE DISCLOSURE

This disclosure relates generally to audience measurement, and, moreparticularly, to methods and apparatus to verify and/or correct medialineup information.

BACKGROUND

Television measurement has traditionally been performed using methodssuch as having panelists keep a log or diary of television viewingand/or using physical meter devices to detect television usage in anautomated fashion.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system to verify and/or correctclickstream data.

FIG. 2 is a block diagram of an example device to implement the exampleclickstream processing system of FIG. 1.

FIG. 3 is a block diagram of an example device to implement the examplemedia presentation data collector of FIG. 1.

FIG. 4 is pseudocode representative of an example script to generatemedia presentation data to verify and/or correct clickstream data.

FIG. 5A is a table representative of example lineup information providedby the example media provider of FIG. 1.

FIG. 5B is a table representative of example program scheduleinformation provided by the example media provider of FIG. 1.

FIG. 6 is a table representative of a media presentation log includingmedia presentation data collected via the example media presentationdata collector of FIGS. 1 and/or 3.

FIG. 7 is a flowchart representative of example instructions which maybe executed to implement the example clickstream processing system ofFIGS. 1 and/or 2 to generate ratings information from clickstream data.

FIG. 8 is a flowchart representative of example instructions which maybe executed to implement the example clickstream processing system ofFIGS. 1 and/or 2 to verify channel mappings based on collected mediapresentation data.

FIGS. 9A and 9B are a flowchart representative of example instructionswhich may be executed to implement the example clickstream processingsystem of FIGS. 1 and/or 2 to correct lineup information.

FIG. 10 is a flowchart representative of example instructions which maybe executed to implement the example media presentation data collectorof FIGS. 1 and/or 3 to collect media presentation data.

FIG. 11 is a block diagram of an example processor platform capable ofexecuting the instructions of FIGS. 7, 8, 9A, 9B, and/or 10 to implementthe clickstream processing system and/or the media presentation datacollector of FIGS. 1, 2, and/or 3.

The figures are not to scale. Wherever appropriate, the same referencenumbers will be used throughout the drawing(s) and accompanying writtendescription to refer to the same or like parts.

DETAILED DESCRIPTION

Television exposure and/or consumption can be measured using return pathdata from cable television set top boxes. Return path data, alsoreferred to herein as clickstream data, is data that indicates whatchannel is being viewed by a set top box in a home and the date and timeof tuning. The return path data for a set top box may includeinteraction information (e.g., commands received by the set top box,timing of the commands) and/or status information (e.g., channel tunedby the set top box). Using return path data to perform audiencemeasurement has a relatively low cost to obtain tuning data for a largeportion of the population. However, return path data can cause erroneousresults unless the data is monitored and corrected. By monitoring returnpath data and providing corrections to the crediting component of thesystem, return path data can provide accurate tuning information.Additionally, because return path data or clickstream data is notnecessarily associated with demographic or other characteristicinformation describing the audiences, demographic and/or othercharacteristic information is determined using other measurementmethods, such as surveys, and applied to the audience data.

A media provider (e.g., cable operator, satellite operator, multi-sourceoperator, radio station, etc.) provides a selection of viewing choicesor channels to subscribers. Viewing choices include networks and/orstations. A media provider assigns networks and/or stations to discretechannels. For example, a media provider may assign channel position 3 tothe (geographically) local ABC affiliate station and assign channel 4for the (national) TNT network. However, different media providers mayassign the networks and/or stations to different channels, and/or thesame media provider may assign the networks and/or stations to differentchannels in different geographic areas.

Lineup information (e.g., a channel lineup) for a media providerincludes the assignment of each network and/or station to a respectivechannel. The lineup information can be provided by the media provider,or by a third party such as Tribune Media Services. In some examples,the lineup information includes media identifiers (e.g., program titles,media identification numbers, etc.) for programming scheduled to bepresented on each of the channels and the times at which the programmingis scheduled to be presented. In some cases, a media provider may changeits channel lineup for one or more subscribers (e.g., in a particulargeographic area) and/or re-organizing geographic areas and/or channellineups without notifying the appropriate entities of such changes (orinforming such entities at a later time). Example methods and apparatusdisclosed herein may use the media identifiers to verify the lineupinformation.

In some examples, a validation site is used to generate mediapresentation data to verify that the channel mappings associated withreturn path data are accurate. Based on the monitoring at a verificationsite, example methods and apparatus disclosed herein monitor clickstreamdata (or return path data) from a media provider and/or correct theclickstream data.

In some examples, a validation site includes a media presentation device(e.g., a television), a set top box, and a media presentation datacollector equipped to send remote control commands to tune the set topbox. Example methods and apparatus disclosed herein provide the mediapresentation data collector with a script to 1) tune the set top boxbased on the channel lineup of a media provider and 2) collect mediapresentation data (e.g., signatures and/or watermarks) from the mediapresentation device associated with the set top box. Each channelavailable from the media provider is tuned for an amount of time whilemedia signals (e.g., audio and/or video signals) and/or mediapresentation data (e.g., signatures, codes, and/or other metadata) arecollected from the channel (e.g., via output from the media presentationdevice). In some examples, non-tuning commands are also issued to theset-top box, such as volume changes, guide display commands, mutecommand, etc.

In examples disclosed herein, media presentation data collectors receivemedia signals from the media presentation device (e.g., a television).For example, the media presentation data collector includes a microphoneor other audio capture device to receive free field (e.g., ambient)audio output by the media presentation device. Example methods andapparatus disclosed herein may use any method(s) to identify the tunedchannel and/or media, such as matching audio signatures to referencesignatures (e.g., to identify media presented at a particular time,which may subsequently be matched to a channel and a station and/ornetwork using a program schedule) and/or decoding audio watermarks(e.g., to obtain a code identifying a network and/or station).

The media presentation data is sent to a clickstream processing systemin near real-time and/or at some periodic or aperiodic interval. In someexamples, in addition to receiving the media presentation data, methodsand apparatus disclosed herein receive the clickstream data (or returnpath data) associated with the set top box employed at the validationsite (e.g., a validation set top box). Example methods and apparatusdetermine whether the clickstream data for the validation set top box isconsistent with the script (e.g., tuning and/or non-tuning channels).For example, the clickstream data for the validation set top box may becompared to the commands programmed in the script to verify that anindication in the clickstream that a given command (e.g., command A) (orsequence of commands) that occurred (e.g., at a particular time) is thesame command (or sequence of commands) that was to be sent to thevalidation set top box according to the script (e.g., for the sametime).

In some examples, the non-tuning commands executed in the script arevalidated against meter data. For example, when the mute key is engagedfor a duration specified in the script, no audio signals should bereceived at the sensor. Example methods and apparatus disclosed hereinalso validate trick mode commands such as pause, fast forward andreverse.

After verifying the media presentation data and/or the clickstream datafrom the verification site, example methods and apparatus disclosedherein verify and/or correct lineup information supplied by the mediaprovider and/or by a third party. For example, based on the script andthe channel lineup information, example methods and apparatus disclosedherein verify each discrete channel to confirm that the station ornetwork available on that channel matches what the lineup informationindicates. For channels that do not match the lineup information, someexample methods and apparatus disclosed herein correct the channels inthe lineup information. In some examples, the verification and/orcorrection includes comparing codes extracted at the verification siteto known codes (e.g., watermarks) of networks and/or stations.Additionally or alternatively, the verification and/or correctionincludes comparing signatures representative of media presented at theverification site to reference signatures of reference media,identifying the media based on the comparisons, and using a programschedule to determine a channel, network, and/or station on which theidentified media is scheduled to be presented.

Example methods and apparatus disclosed herein generate reportsincluding discrepancies identified in channel lineup information and/ordisagreement between clickstream data commands and scripted commands.After identifying and/or correcting identified discrepancies in thelineup information, example methods and apparatus disclosed herein usethe lineup information to perform crediting using the clickstream dataand/or to apply corrections to the crediting process. For example, wherechannel lineup information indicated that the TNT network should be onchannel 4, but in fact the TNT network appeared on channel 5, methodsand apparatus disclosed herein correctly apply credit for viewing onchannel 5 derived from clickstream data to the TNT network (and mediapresented thereon).

Audio watermarking is a technique used to identify media such astelevision broadcasts, radio broadcasts, advertisements (televisionand/or radio), downloaded media, streaming media, prepackaged media,etc. Existing audio watermarking techniques identify media by embeddingone or more audio codes (e.g., one or more watermarks), such as astation and/or network identifier and/or media identifying information(e.g., a code mapped to the media) into an audio and/or video componentof media. In some examples, the audio and/or video component is selectedto have a signal characteristic sufficient to hide the watermark fromhuman detection (e.g., masked from hearing). This is sometimes referredto as stenographic encoding. As used herein, the terms “code” or“watermark” are used interchangeably and are defined to mean anyidentification information (e.g., an identifier) that may be inserted orembedded in the audio or video of media (e.g., a program oradvertisement) for the purpose of identifying the media or for anotherpurpose such as tuning (e.g., a packet identifying header). As usedherein “media” refers to audio and/or visual (still or moving) contentand/or advertisements. To identify watermarked media, the watermark(s)are extracted and used to access a table of reference watermarks thatare mapped to a station and/or network and/or to media identifyinginformation.

Another type of media identifier used in example methods and apparatusdisclosed herein is signatures or fingerprints. Unlike media monitoringtechniques based on codes and/or watermarks included with and/orembedded in the monitored media, fingerprint or signature-based mediamonitoring techniques generally use one or more inherent characteristicsof the monitored media during a monitoring time interval to generate asubstantially unique proxy for the media. Such a proxy is referred to asa signature or fingerprint, and can take any form (e.g., a series ofdigital values, a waveform, etc.) representative of any aspect(s) of themedia signal(s)(e.g., the audio and/or video signals forming the mediapresentation being monitored). Good signatures are repeatable whenprocessing the same media presentation, but are unique relative to other(e.g., different) presentations of other (e.g., different) media.Accordingly, the term “fingerprint” and “signature” are usedinterchangeably herein and are defined herein to mean a proxy foridentifying media that is generated from one or more inherentcharacteristics of the media.

Signature-based media monitoring generally involves determining (e.g.,generating and/or collecting) signature(s) representative of a mediasignal (e.g., an audio signal and/or a video signal) output by amonitored media device and comparing the monitored signature(s) to oneor more reference signatures corresponding to known (e.g., reference)media sources. Various comparison criteria, such as a cross-correlationvalue, a Hamming distance, etc., can be evaluated to determine whether amonitored signature matches a particular reference signature. When amatch between the monitored signature and one of the referencesignatures is found, the monitored media can be identified ascorresponding to the particular reference media represented by thereference signature that matched the monitored signature. Becauseattributes, such as an identifier of the media, a presentation time, abroadcast channel, etc., are collected for the reference signature,these attributes may then be associated with the monitored media whosemonitored signature matched the reference signature. Example systems foridentifying media based on codes and/or signatures are long known andwere first disclosed in Thomas, U.S. Pat. No. 5,481,294, which is herebyincorporated by reference in its entirety.

Examples disclosed herein solve problems related to ensuring clickstreamdata accuracy. Clickstream data is digital computer data (e.g., set topbox data, PC data, data related to any other type of media accessdevice). Example methods and apparatus disclosed herein enhance theefficiency of correcting (digital) clickstream data to adjust forinaccuracies in reported channel lineups by using computers toautomatically correct the channel lineups and using the computers toapply the corrections to the clickstream data. Automatic correction ofchannel lineups performed by example methods and apparatus disclosedherein enhances the accuracy of audience measurement data that relies onthe clickstream data (which, in turn, relies on correct channellineups). Verifying and/or correcting channel lineups also reduces oreliminates manual data correction, which increases costs of performingaudience measurement. Example methods and apparatus disclosed herein use(digital) media presentation data, such as watermarks stored in mediaand/or digital fingerprints representative of the media, to enableautomatic verification and/or correction of a mapping between a networkand/or station and a channel number.

By leveraging the automatic verification and/or correction of a channellineup to correct clickstream data that relies on that channel lineup,example methods and apparatus disclosed herein can correct clickstreamdata from hundreds or thousands of channel lineups (e.g., for differentgeographic areas and/or different multi-system operators such as cabletelevision providers and/or satellite television providers) in acost-effective manner. Example methods and apparatus disclosed hereinbenefit the field of audience measurement by increasing the accuracy ofclickstream data which, in turn, improves the accuracy of measurementsof television channel audiences. Example methods and apparatus disclosedherein conserve computing resources and/or network resources used tomonitor audiences by reducing or eliminating the need to identify andsend messages to multi-channel system operators (MSO) to verify channelsin large numbers of distinct channel lineups for correspondinggeographic regions. For example, example methods and apparatus disclosedherein reduce or eliminate the need for a computer or a person toidentify a MSO for a geographic region, communicate a channelverification request and the geographic region, receive the channelverification information, and apply the channel verification to alineup, which further requires the MSO to perform a lookup of thechannel to a station and/or network. This reduction or elimination ofcomputing and/or network resource requirements frees up these resourcesfor other beneficial uses.

FIG. 1 illustrates an example system 100 to verify and/or correctclickstream (or return path) data. The example system 100 of FIG. 1 maybe used to verify clickstream data with less manual identification ofchannels compared to known methods of correcting clickstream data. Insome examples, no manual identification of channels is involved.

The example system 100 of FIG. 1 includes a clickstream processingsystem 102, which obtains return path data or clickstream data from amedia provider 104, verifies and/or corrects the clickstream data,and/or generates ratings information for the media (e.g., programs,advertisements, etc.). The example clickstream processing system 102 isassociated with an audience measurement entity, such as The NielsenCompany (US), LLC, which generates audience ratings for media. The mediaprovider 104 of FIG. 1 may be a multi-system operator such as a cabletelevision provider. However, the media provider 104 may be any type ofcontent provider capable of providing clickstream or return path data.

The clickstream processing system 102 of the illustrated example obtainsmedia presentation data from a verification site 106. The verificationsite 106 is physically located such that the verification site 106 iscapable of receiving a television lineup (e.g., set of channels andcorresponding channel numbering scheme) corresponding to clickstreamdata provided by the media provider 104. The physical location mayinclude, for example, a geographic location or area in which the mediaprovider 104 uses a particular mapping of channels to networks and/orstations. The example verification site 106 may be, but is notnecessarily, a reference site that is independent of any panel-basedmeasurement that may also be occurring in or near the geographiclocation or area of the verification site 106.

The clickstream data is collected from set top boxes by the mediaprovider 104 and made available for media measurement. In some examples,the media provider 104 collects clickstream data from physical set topboxes as well as devices that function as tuners or set top boxes (e.g.,a computing device that includes a cable tuning card and/or softwarethat enables the computing device (e.g., a computer, a tablet, etc.) toreceive media from the media provider 104 and provide clickstream data).Clickstream data can be obtained from the media provider 104 in a rawformat, or can be processed by the media provider 104 to perform somevalidation and/or formatting of the data prior to making the dataavailable external to the media provider 104.

The example clickstream processing system 102 obtains lineup information110 from the media provider 104 and/or from a lineup data provider 108(e.g., TV Guide®). In some examples, multiple verification sites 106 maybe used to generate media presentation data for the clickstreamprocessing system 102 to verify and/or to correct clickstream dataprovided for multiple areas that have different channel lineups. Theexample clickstream processing system 102 obtains lineup information 110for each such channel lineup (e.g., from the respective media providers104 and/or from the lineup data provider 108). An example of lineupinformation is described below with reference to FIG. 5B.

The example verification site 106 of FIG. 1 is associated with a firstphysical area (within which a particular channel mapping or lineupinformation scheme is used by the media provider 104). The verificationsite 106 of FIG. 1 includes a media presentation data collector 112, aremote control 114, and a sensor 116. The example media presentationdata collector 112 transmits commands via the remote control 114 to aset top box 118 that receives the monitored service (e.g., cable and/orsatellite television, streaming media, video on demand, etc.) from themedia provider 104. Example remote controls include an infrared remotecontrol, a radio-frequency remote control, a network-based remotecontrol, a Bluetooth remote control, and/or any other type of remotecontrol device.

The set top box 118 of the illustrated example tunes to channelsaccording to the commands received from the remote control 114 andpresents the media playing on the tuned channel on a media presentationdevice 120. The media presentation device may be a television, speakers,a radio, or any other type of media presentation device. While theexample of FIG. 1 includes a set top box 118 to tune to channels, theexample set top box 118 may be implemented using a personal computer(e.g., a home theater personal computer (HTPC)) and a CableCARD orsimilar tuning device, a video game console, and/or any other devicecapable of receiving media from the media provider 104 and outputtingthe media as audio and/or video via the presentation device 120. In someexamples, the set top box 118, the media presentation device 120, and/orthe media presentation data collector 112 are integrated into a singledevice. For example, a computer may implement the presentation device120 via a display and/or speakers to present the media, the set top box118 via a tuner card, and the media presentation data collector 112 viaa software program that captures the audio in the presented media fordetecting watermarks and/or generating fingerprints (e.g., signatures).

The example sensor 116 of FIG. 1 is positioned to receive audio signalsoutput from the media presentation device 120. In some examples, thesensor 116 is a microphone that captures ambient audio proximate to themedia presentation device 120. In some other examples, the sensor 116includes a hard-wired connection to the media presentation device 120and/or to the set top box 118 to receive the media signals. In someexamples, the sensor 116 is communicatively coupled (e.g., networked)between the set top box 118 and the media presentation device 120 tosnoop media signals including audio, video, and/or encoded mediasignals. Alternatively, the example sensor 116 may simply receive outputaudio and/or video signals directly from the set top box 118. In somesuch examples, the example media presentation device 120 is omitted.

In the example of FIG. 1, the media presentation data collector 112generates media presentation data (e.g., codes, signatures, etc.) fromthe media signals (e.g., audio and/or video signals) collected from theset top box 118 and/or the media presentation device 120. For example,the media presentation data collector 112 of the illustrated exampleextracts watermarks from captured audio and/or video signals and/orgenerates signatures (fingerprints) representative of the audio and/orvideo.

In some other examples, the media presentation data collector 112collects metadata that is extracted from the media by the set top box118, by the media presentation device 120. For example, the set top box118 may extract metadata in the form of ID3 tags (or any other format)and output the extracted metadata to the media presentation datacollector 112 via a wired or wireless communications connection. In someexamples, the extracted ID3 tags contain codes corresponding towatermark codes. Example methods and apparatus to embed and/or extractmetadata from a data stream that may be performed by the example set topbox 118 and/or the example media presentation data collector 112 of FIG.1 are disclosed in U.S. patent application Ser. No. 13/181,147, filed onJul. 12, 2011, U.S. patent application Ser. No. 13/341,661, filed onDec. 30, 2011, U.S. patent application Ser. No. 13/443,596, filed onApr. 10, 2012, U.S. patent application Ser. No. 13/455,961, filed onApr. 25, 2012, U.S. patent application Ser. No. 13/767,548, filed onFeb. 14, 2013, U.S. patent application Ser. No. 13/778,108, filed onFeb. 26, 2013, U.S. patent application Ser. No. 13/793,959, filed onMar. 11, 2013, U.S. patent application Ser. No. 13/793,974, filed onMar. 11, 2013, U.S. patent application Ser. No. 13/793,983, filed onMar. 11, 2013, and/or U.S. patent application Ser. No. 13/793,991, filedon Mar. 11, 2013. The entireties of U.S. patent application Ser. No.13/181,147, U.S. patent application Ser. No. 13/341,661, U.S. patentapplication Ser. No. 13/443,596, U.S. patent application Ser. No.13/455,961, U.S. patent application Ser. No. 13/767,548, U.S. patentapplication Ser. No. 13/778,108, U.S. patent application Ser. No.13/793,959, U.S. patent application Ser. No. 13/793,974, U.S. patentapplication Ser. No. 13/793,983, and U.S. patent application Ser. No.13/793,991 are hereby incorporated by reference.

Watermarks, signatures, metadata, and the like, are collectivelyreferred to herein as media presentation data. The media presentationdata identifies the media presented on one or more channels tuned by theset top box 118, but does not necessarily identify the tuned channelitself.

In the example of FIG. 1, the media presentation data collector 112collects media presentation data from multiple channels (e.g., onechannel at a time) to facilitate the automatic identification of each ofthe multiple channels and/or verify a mapping between the channel and anetwork and/or station. The example media presentation data collector112 generates a report including the media presentation data, timestampsassociated with collection of the media presentation data, and thechannel associated with the media presentation data. The mediapresentation data collector 112 identifies the tuned channel(s) fromwhich the media presentation data are collected by comparing thetimestamp(s) associated with the media presentation data to a log oftimestamped actions performed while executing a script. The examplemedia presentation data collector 112 of FIG. 1 receives script(s) forcontrolling the verification set top box 118 from the exampleclickstream processing system 102 via, for example, a communicationsnetwork. The log records times at which each of the multiple channels istuned by the verification set top box 118 in accordance with the script.The script may specify channel information (e.g., the channel(s) to betuned by the verification set top box 118) explicitly (e.g., via acondition such as “if X, then tune to channel Y”) and/or implicitly(e.g., based on a time at which the script is executed and programmeddelays in the script). The example media presentation data collector 112of the illustrated example reports channel information based on an orderof tuning the verification set top box 118 that is specified in thescript.

Both the media presentation data (e.g., codes, signatures, etc.) and thechannel information (e.g., channel(s) tuned by the verification set topbox 118) are timestamped. The timestamps represent time(s) and/ordate(s) at which the media signals were collected and/or the time(s)and/or date(s) at which a corresponding channel was tuned. Thisassociation may be done through, for example, matching timestamps. Thecorresponding channel is a channel to which the set top box 118 wastuned when the media signals were collected. Each item of mediapresentation data (e.g., each signature and/or extracted watermark) maybe associated with a timestamp and/or a channel identified in thechannel information. Additionally or alternatively, groups of the mediapresentation data (e.g., time-adjacent codes, time-adjacent signatures,etc.) may be marked with a same timestamp and/or channel identifier.

When the media presentation data has been collected for each of thechannels (e.g., by performing the actions in the script and collectingmedia presentation data from the media presentation device), the examplemedia presentation data collector 112 transmits the media presentationdata, the timestamps, and the channels to the clickstream processingsystem 102. Using the media presentation data and the channelinformation, the example clickstream processing system 102 of FIG. 1verifies and/or corrects the lineup information 110 for the physicalarea associated with the set top box 118 by, for example, determiningthat the mappings of channels to channel numbers (e.g., ESPN is channel30, CNN is channel 24, etc.) are the same as reported in the lineupinformation 110. Example methods and apparatus to correct lineupinformation are described in more detail below.

The example clickstream processing system 102 of FIG. 1 determinesratings information based on the clickstream data provided by the mediaprovider 104 and based on the verified and/or corrected lineupinformation. For example, the example clickstream processing system 102may determine the number of households tuned to each channel and/orprogram according to the clickstream data.

FIG. 2 is a block diagram of an example implementation of the exampleclickstream processing system 102 of FIG. 1. The example clickstreamprocessing system 102 of FIG. 2 includes a script generator 202, achannel verifier 204, and a clickstream media crediter 206.

The example script generator 202 of FIG. 2 generates scripts to beexecuted by a media presentation data collector (e.g., the mediapresentation data collector 112 of FIG. 1). The example scripts mayinclude instructions to cause the media presentation data collector 112to generate and/or transmit commands to the set top box 118 (e.g.,tuning commands), to collect and/or generate media presentation dataand/or tuning information data, and/or to transmit the mediapresentation data to the clickstream processing system 102. The scriptmay be customized for a particular verification site, a type of remote114, a type of set top box 118, a monitored area, a particular aparticular study, and/or a type of media presentation data collector112. The example script generator 202 may transmit the generatedscript(s) to corresponding media presentation data collectors (e.g., themedia presentation data collector 112 of FIG. 1) for collection of mediapresentation data.

Based on the media presentation data and/or channel information returnedby the media presentation data collector 112, the example channelverifier 204 of FIG. 2 verifies lineup information 110 received from themedia provider 104 and/or from the lineup data provider 108 of FIG. 1.For example, the channel verifier 204 determines, for each channel(e.g., each channel from which media presentation data was received fromthe media presentation data collector 112 as indicated by the channelinformation, and/or each channel included in the lineup information110), whether the media presentation data collected while tuned to thechannel matches reference data. In some examples, the reference data isrepresentative of the network/station assigned to a channel according tothe lineup information 110. Additionally or alternatively, the referencedata is representative of media presented on the channel and/or thenetwork and/or station according to the lineup information and/orprogram schedule information. based on the timestamp and the channelassociated with the media presentation data. The reference data may beselected based on the type of media presentation data collected by themedia presentation data collector 112.

To verify and/or correct lineup information, the example channelverifier 204 of FIG. 2 includes a lineup interpreter 208 and a mediadata comparator 210. The media data comparator 210 includes a watermarkidentifier 212, a watermark database 214, a signature comparator 216,and a signature database 218. In some examples, the media datacomparator 210 exclusively uses watermarks and omits the signaturecomparator 216 and the signature database 218. In other examples, themedia data comparator 210 exclusively uses signatures and omits thewatermark identifier 212 and the watermark database 214.

The example lineup interpreter 208 of FIG. 2 receives or accesses thelineup information 110 from the media provider 104 and/or the lineupdata provider 108. The lineup information 110 in the example of FIG. 2includes a set of networks and/or stations, and the channels to whichthe set of networks and/or stations are mapped. In some examples, thelineup interpreter 208 determines program schedule information based onthe lineup information and/or a designated time. Example programinformation includes a set of media identifiers (e.g., identifiers ofprograms) for media presented on designated channels at designated times(e.g., designated time slots, such as ½ hour time slots) and/or duringdesignated time ranges (e.g., time ranges defined using start times andend times). The media identifiers may include titles of media, episodenames of media, episode numbers of media, unique media identificationnumbers, and/or any other type of media identifier.

In some examples, the lineup interpreter 208 of FIG. 2 translates thechannel, the network and/or station, the media identifier, and/or thetime to a lookup key. The media data comparator 210 of the illustratedexample uses the resulting lookup key to identify the correct referencedata. The example media data comparator 210 uses the reference data toverify and/or correct the channels in the lineup information 110.

The example media data comparator 210 accesses the script generated bythe script generator 202, obtains the network, station, and/or channelfrom the lineup interpreter 208, and obtains media presentation datafrom the media presentation data collector 112 collected based on thegenerated script. For each channel programmed via the script, theexample media data comparator 210 compares the media presentation data(e.g., watermarks, signatures) collected while the channel is tuned bythe set top box 118 to reference data (identified using the mediaidentifier obtained from the lineup interpreter 208).

In examples in which the watermark identifier 212 identifies a watermark(or code) as a known code (e.g., in the watermark database 214), theexample channel verifier 204 verifies channel information and/orclickstream data using the identified code and the lineup informationidentified by the lineup interpreter 208. For example, the media datacomparator 210 determines whether the code identified by the watermarkidentifier 212 matches a reference code that corresponds to the networkand/or station assigned to the channel on which the identified code wasobserved. For example, the media data comparator 210 determines (fromthe lineup information 110) that channel 1 corresponds to station WABC.The example channel verifier 204 further determines (from the watermarkdatabase 214) that WABC corresponds to a code “01100110.” The examplemedia data comparator 210 may then compare an identified code observedwhen the verification set top box 118 was tuned to channel 1 to thereference code “01100110” to determine whether the codes match. If theidentified code does not match the reference code, the example channelverifier 204 takes corrective steps to determine the correct networkand/or station assigned to the channel on which the code was identified,as discussed in more detail below.

To determine whether watermark data matches reference watermark data,the example watermark identifier 212 of FIG. 2 identifies a networkand/or station corresponding to the watermark. For example, thewatermark may include a string of bits or other symbols (e.g., afifteen-bit binary number or code) that may be decoded into readabledata (e.g., a program title, an episode number, a media identifier, astation identifier and timestamp, etc.) and/or that may be used as anindex to look up a network and/or station in the watermark database 214.When the watermark is used as an index, the example watermark identifier212 obtains (e.g., looks up) the network and/or station (e.g., the ABCnetwork, a local network affiliate station WABC, etc.) based on thewatermark data (e.g., decoded watermark data). The example watermarkidentifier 212 compares the resulting network and/or station identifierto a reference network and/or station identifier determined from thechannel, network, and/or station obtained from the lineup interpreter208.

In other examples, the watermark identifier 212 retrieves a referencewatermark from the watermark database 214 (e.g., using the mediaidentifier received from the lineup interpreter 208 as an index) andcompares the retrieved reference watermark to the watermark datareceived from the media presentation data collector 112. For example,the watermark identifier 212 may determine that the media identifierP09876 received from the lineup interpreter 208 corresponds to areference watermark in the watermark database 214. The example watermarkidentifier 212 compares the reference watermark to the watermarkreceived from the media presentation data collector 112 to determinewhether the watermarks match (e.g., whether the watermarks areidentical).

In examples in which the signature comparator 216 compares signaturesfrom presented media to identify matching signatures (e.g., in thesignature database 218), the example lineup interpreter 208 of FIG. 2translates the network and/or station, the channel, and/or the time to asignature lookup key. For example, the lineup interpreter 208 determinesa media item that is programmed for the channel and the time at whichsignatures were collected by the media presentation data collector 112,based on a program schedule.

The example signature database 218 of FIG. 2 includes mappings ofsignatures obtained from reference media to identifiers of the referencemedia from which the signatures were generated. The example lineupinterpreter 208 uses the media item (e.g., an identifier correspondingto a show and/or episode) to look up a set of reference signaturesgenerated from that media item in the signature database 218. Forexample, the example media data comparator 210 of FIG. 2 may translate afirst program title (e.g., “Chicago Fire”), network (e.g., “NBCaffiliate”), and time (e.g., 03:00 UTC 2013-11-21) to a unique mediaidentifier (e.g., P54321), for which a set of reference signatures canbe obtained from the signature database 218 for comparison.

The signature comparator 216 compares the signatures collected by themedia presentation data collector 112 to the reference signaturesobtained from the signature database 218 to verify and/or correct thechannels in the lineup information 110. The signature comparator 216 mayidentify a match based on, for example, whether a threshold numberand/or percentage of the received signatures match the referencesignatures. For example, the signature comparator 216 of the illustratedexample receives a media identifier P34567 from the lineup interpreter208 and accesses the signature database 218 based on the mediaidentifier P34567 to extract a set of associated reference signatures.The example signature comparator 216 compares signatures collected bythe media presentation data collector 112 (e.g., while the set top box118 is tuned to a channel scheduled to present the media associated withthe media identifier P34567) to the set of reference signatures. Thesignature comparator 216 determines a match based on whether at least athreshold number of the collected signatures (e.g., signaturesrepresenting at least threshold period of time) match referencesignatures. If the collected signatures do not match the referencesignatures, the example channel verifier 204 may initiate correctivesteps to determine the correct network and/or station assigned to thechannel from which the signatures were collected by the mediapresentation data collector 112, as discussed in more detail below.

In some examples, because the media presentation data collector 112 mayonly collect signatures representing a relatively short period of time(e.g., a few minutes) for any given channel, the signature comparator216 may only match a portion of the reference signatures representingreference media to the signatures received from the media presentationdata collector 112.

In some other examples, metadata (e.g., ID3 tags) extracted from themedia is used as a lookup key to identify a station, a network, and/ormedia presented on the channel. For example, the channel verifier 204 ofFIG. 2 may search a database using the metadata as a lookup key, wherethe lookup key is stored in association with the network, the station,and/or the media. Examples of identifying a network, a station, and/ormedia are described in U.S. patent application Ser. No. 13/181,147, U.S.patent application Ser. No. 13/341,661, U.S. patent application Ser. No.13/443,596, U.S. patent application Ser. No. 13/455,961, U.S. patentapplication Ser. No. 13/767,548, U.S. patent application Ser. No.13/778,108, U.S. patent application Ser. No. 13/793,959, U.S. patentapplication Ser. No. 13/793,974, U.S. patent application Ser. No.13/793,983, and U.S. patent application Ser. No. 13/793,991.

When the network and/or station corresponding to an extracted codematches the network and/or station assigned to the channel in the lineupinformation, and/or when a threshold number of signatures (and/or acorresponding media identifier) match reference signatures (and/or acorresponding reference media identifier), the example channel verifier204 confirms that the channel mapping is correct (e.g., annotates thelineup information 110) and/or confirms that the lineup information 110is correct for the channel.

On the other hand, when the media presentation data does not match thereference data, the example channel verifier 204 corrects the lineupinformation 110 for A) the channel to which the verification set top box118 was tuned when the non-matching media presentation data wascollected and/or B) the network and/or station assigned to the channelaccording to the lineup information 110. For example, if the mediapresentation data collected at a first time when the verification settop box 118 is tuned to channel 2 does not match the reference dataassociated with the network and/or station assigned to channel 2according to the lineup information 110, the example channel verifier204 determines a network, station, and/or media that is actually mappedto channel 2. Additionally or alternatively, the example channelverifier 204 determines a channel to which the network and/or stationthat is incorrectly mapped to channel 2 is actually assigned.

To determine a network and/or station that is actually mapped to thenon-matching channel number, the example channel verifier 204 of theillustrated example compares A) the media presentation data (e.g.,signatures) collected when the set top box 118 was tuned to the channel,to B) reference data (e.g., reference signatures) for media presented onother channels (e.g., according to the program schedule) during the timeperiod in which the media presentation data was collected. For example,the lineup interpreter 208 of FIG. 2 determines a time period duringwhich the media presentation data was collected (e.g., 12:02 P.M. to12:04 P.M. on Nov. 18, 2013). The example lineup interpreter 208 of theillustrated example also determines media identifiers for mediapresented on other channels during the corresponding time period (e.g.,the 12:02 P.M. to 12:04 P.M. time period on Nov. 18, 2013 and/or, moregenerally, the 12:00 P.M. to 12:30 P.M. time slot on Nov. 18, 2013). Theexample media data comparator 210 (e.g., via the signature comparator216) compares the media presentation data to the reference dataassociated with the media presented on the other channels until a matchis found.

If a match is found between the media presentation data and referencedata associated with another channel, the example channel verifier 204corrects the lineup information 110 such that the channel is associatedwith the correct network and/or station. On the other hand, if no matchis found, the example channel verifier 204 of the illustrated exampleattempts to verify the channel using alternate media presentation data(e.g., media presentation data collected at another time) or annotatethe channel for manual verification.

Additionally or alternatively, the example media data comparator 210 maydetermine the network and/or station mapped to the non-matching channelby comparing a code extracted while tuned to the channel to other codesin the watermark database 214. By comparing the extracted code to thecodes in the watermark database 214, the example media data comparator210 identifies the network and/or station matching the code. Because thecode was observed on the non-matching channel, the network and/orstation matching the observed code can be mapped to the non-matchingchannel in the lineup information 110.

For example, if network affiliate WCBS is mapped to channel 2 in thelineup information 110 and the watermark identifier 212 determines thatthe code extracted by the media presentation data collector 112 when theverification set top box 118 was tuned to channel 2 does not correspondto WCBS, the example watermark identifier 212 determines which of thecodes in the watermark database 214 matches the extracted code. In thisexample, the watermark identifier 212 determines that the extracted codematches WABC and the channel verifier 204 modifies the lineupinformation 110 to map WABC to channel 2.

In some examples, the media data comparator 210 determines a networkand/or station mapped to the non-matching channel by looking up metadata(e.g., ID3 tags) extracted while tuned to the channel in a metadatadatabase (e.g., generating a database query using the metadata as akey). The example metadata may identify the channel, the network and/orstation, and/or the media being presented. If the query results in amatch, the example media data comparator 210 may determine that thenetwork, station, and/or media are associated with the channel tuned bythe set top box at the time the metadata was extracted. Examples ofidentifying a channel, network, station, and/or media based on metadataextracted from the media are described in U.S. patent application Ser.No. 13/181,147, U.S. patent application Ser. No. 13/341,661, U.S. patentapplication Ser. No. 13/443,596, U.S. patent application Ser. No.13/455,961, U.S. patent application Ser. No. 13/767,548, U.S. patentapplication Ser. No. 13/778,108, U.S. patent application Ser. No.13/793,959, U.S. patent application Ser. No. 13/793,974, U.S. patentapplication Ser. No. 13/793,983, and U.S. patent application Ser. No.13/793,991.

To determine the channel on which the non-matching reference data (e.g.,signatures associated with media scheduled for presentation on thechannel) was presented using signatures, the example signaturecomparator 216 compares the non-matching signatures (and/or signaturescorresponding to the same channel as the non-matching signatures butcorresponding to media presented at times that are earlier and/or laterthan the non-matching signatures) to alternate signatures collected bythe media presentation data collector 112 on other channels. Because themedia presentation data collector 112 of FIG. 1 collects mediapresentation data (e.g., signatures) for different channels at differenttimes (e.g., collects signatures for channel 2 from 12:02 PM to 12:04PM, collects signatures for channel 3 from 12:04 P.M. to 12:06 P.M.,etc.), the example channel verifier 204 may need to expand the potentialreference signatures to be compared to the non-matching signatures todetermine a match. For example, if Program A did not match to channel 2,the channel verifier 204 of the illustrated example may check signaturesobtained from channels 3, 4, 5, and so on, to determine whether ProgramA (or programs scheduled before and/or after Program A) matches mediacollected from one of the channels 3, 4, 5, and so on.

The expanded potential reference signatures may include, for example,reference signatures associated with media presented on the same channelas the non-matching reference signatures during the time period duringwhich the media presentation data collector 112 was collectingsignatures for the channels associated with the script. For example, ifthe script causes the media presentation data collector 112 to collectmedia presentation data from 12:00 P.M. to 2:45 P.M. on a designatedday, the lineup interpreter 208 determines media identifiers for thechannel corresponding to the non-matching reference signatures for thetimes between 12:00 P.M. and 2:45 P.M. on the designated day.

The example signature comparator 216 compares the signatures for eachchannel to reference data associated with the media identifier (e.g.,received from the lineup interpreter 208) to identify a channel thatpresented the non-matching reference data (or, alternatively, identifythe channel assigned to the network and/or station associated with thenon-matching reference data). In the example of FIG. 2, the signaturecomparator 216 determines a portion of the reference signatures thatwere presented at a time at which the signatures for a particularchannel was collected. The signature comparator 216 may use anapproximate window determined based on the scheduled time of thereference media and based on the position of the signatures within themedia. In some examples, the media data comparator 210 determines theportion of the reference signatures for the media presentation datacollected from each channel.

To increase the efficiency of identifying the channel on which the mediacorresponding to the non-matching reference signatures was presented,the example signature comparator 216 compares the portions of thereference signatures to the signatures collected at the same time priorto comparing other reference signatures to the collected signatures. Insome examples, the signature comparator 216 omits comparing thecollected signatures for those channels, networks, and/or stations thathave already been confirmed or corrected.

Additionally or alternatively, the example watermark identifier 212 ofFIG. 2 determines the channel on which the non-matching reference data(e.g., watermarks extracted by the media presentation data collector112) was presented to correct the lineup information 110. For example,the watermark identifier 212 may determine the channel by comparing thenon-matching reference code to codes extracted by the media presentationdata collector 112 when the verification set top box 118 was tuned tochannels other than the channel to which the non-matching reference codewas incorrectly mapped (according to the lineup information 110). Byidentifying a code collected by the media presentation data collector112 as matching the non-matching reference code, the example watermarkidentifier 212 determines the channel to which the network and/orstation corresponding to the non-matching reference code is assigned.The media data comparator 210 may use any other type of metadata todetermine the e channel on which the non-matching reference data (e.g.,metadata extracted by the media presentation data collector 112) waspresented.

For example, if the code “01010101” maps to network affiliate KNBC,which is incorrectly mapped to channel 6 in the lineup information 110,the example watermark identifier 212 searches the media presentationdata obtained from the media presentation data collector 112 todetermine which of the channels was tuned when the code “01010101” wasextracted. In this example, the channel 7 was tuned by the verificationset top box 118 when the media presentation data collector 112 extractedthe code “01010101.” Accordingly, the example channel verifier 204automatically corrects the lineup information 110 to reflect the mappingof KNBC to channel 7.

When the channel verifier 204 has verified the correctness of the lineupinformation 110 and/or corrected channel mappings in the lineupinformation 110, the example clickstream media crediter 206 of FIG. 2corrects clickstream data generated by the media provider 104. Forexample, the clickstream media crediter 206 may process the clickstreamdata to determine a number of set top boxes tuned to each channel numberand/or presented media item (e.g., program, advertisement). Theclickstream data includes channel tuning data for set top boxes. Theclickstream media crediter 206 of the illustrated example determines thechannels tuned by each of the set top boxes represented in theclickstream data. For example, for a given set top box, the exampleclickstream media crediter 206 interprets the clickstream data toidentify tuning commands, power commands, and/or other clickstream dataand associated timestamps. The clickstream data and timestamps indicatethe channel(s) to which the set top box was tuned. By applying theclickstream data to the channel mappings in the lineup information, theclickstream media crediter 206 determines the audiences for theprograms. In this example, the clickstream media crediter 206 thenapplies the verified and/or corrected lineup information to credit eachchannel and/or media item (e.g., program) with the audience determinedfrom the clickstream data.

The example clickstream processing system 200 of FIG. 2 further includesa clickstream data verifier 220. Subsequent to execution of the scriptgenerated by the script generator 202, the example clickstream dataverifier 220 receives clickstream data associated with the verificationsite 106 of FIG. 1 (e.g., clickstream data for the set top box 118). Theclickstream data verifier 220 compares the clickstream data (e.g.,commands identified in the clickstream data) to the commands included inthe script to determine the clickstream data that corresponds to eachcommand executed by the set top box 118. In some other examples, theclickstream data verifier 220 verifies that the clickstream data matchesknown commands and/or identifies discrepancies between clickstream dataexpected based on the script and the actual clickstream data providedfrom the media provider 104 for the verification site 106.

The example clickstream media crediter 206 of FIG. 2 may use theverified and/or corrected clickstream data mapping to interpret theclickstream data for audience measurement. For example, the clickstreammedia crediter 206 of the illustrated example may determine, based onthe clickstream data, an audience (e.g., a number of set top boxestuned) for each channel and/or media presentation, determine trick playand/or time-shifted media presentations, and/or identify muted mediapresentations, among other things. Determining an audience for media mayinclude, for example, summing a number of set top boxes for which theassociated clickstream data indicates that the tuned channel andassociated timestamp corresponding to the media. Certain commands maycause set top box tuning in some contexts but not in other contexts.

FIG. 3 is a block diagram of an example implementation of the examplemedia presentation data collector 112 of FIG. 1. The example mediapresentation data collector 112 of FIG. 3 receives script(s) from theexample clickstream processing system 102 of FIGS. 1 and/or 2. Based onthe script(s), the example media presentation data collector 112 of FIG.3 collects media presentation data and channel information, and providesthe collected media presentation data and channel information, times atwhich the media presentation data and channel information is collected,and channels to which the set top box 118 was tuned to the clickstreamprocessing system 102.

The example media presentation data collector 112 of FIG. 3 includes ascript interpreter 302, a transmitter interface 304, a sensor interface306, a signature generator 308, a watermark extractor 310, a storagedevice 312, and a media presentation report generator 314.

The example script interpreter 302 of FIG. 3 receives a script from theexample clickstream processing system 102. The script interpreter 302executes the script instructions to directly control the transmitterinterface 304 (e.g., to generate output transmissions) and/or the sensorinterface 306 (e.g., to collect, process, and/or store input signals).In some examples, the script interpreter 302 is provided with a scriptduring setup and/or configuration of the media presentation datacollector 112 at the verification site 106. The script is periodicallyand/or aperiodically updated to, for example, include newly added and/orreconfigured channels available from the media provider 104 at the settop box 118. The script may be executed periodically (e.g., based on aclock), aperiodically (e.g., in response to one or more events), inresponse to a request from the clickstream processing system 102, and/orat any other time.

The example transmitter interface 304 of FIG. 3 provides an interfacebetween the script interpreter 302 and the example remote control 114 ofFIG. 1. For example, the transmitter interface 304 may include atranslator to translate commands from a format used in the script to aformat used by the remote control 114 (e.g., universal serial bus (USB)messages). In some other examples, the transmitter interface 304converts the commands directly to electromagnetic signals (e.g., radiofrequency signals, infrared frequency signals, Bluetooth signals, etc.)to be transmitted directly by the example remote control 114 that maynot have a signal converter. The transmitter interface 304 outputs thecommands to cause the set top box 118 to tune to selected channels andto thereby cause the media presentation device 120 to output mediasignals (e.g., audio and/or video signals).

The example sensor interface 306 of FIG. 3 receives media signals and/ordata from the example sensor 116 of FIG. 1. In some examples, the sensorinterface 306 is selectively instructed by the script interpreter 302 tocollect and/or store the media signals and/or data. For example, thesensor interface 306 may be controlled to collect and/or store signalsand data during time periods following the transmitter interface 304issuing commands to the remote control 114. At other times, the examplesensor interface 306 may be selectively instructed to ignore or discardinput, such as when no media of interest is being presented via themedia presentation device 120. The example media signals and/or data mayinclude audio signals (e.g., analog audio recorded via a microphonesensor), video signals (e.g., analog video recorded via an image sensoror received from a video line out connection), and/or digital dataversions (e.g., digital samples) of audio and/or video (e.g., digitizedaudio, digitized video).

The example sensor interface 306 provides the media signals and/or datato the signature generator 308 and/or to the watermark extractor 310.The example signature generator 308 of FIG. 3 generates signatures orfingerprints of the media signals and/or data. For example, thesignature generator 308 may generate signatures of overlapping blocks ofaudio received via the sensor interface 306 to characterize the audiopresented on a tuned channel during a time period. Example methods andapparatus to implement the example signature generator 308 are describedin U.S. Pat. No. 8,600,531. However, any other method of signaturing orfingerprinting may additionally or alternatively be used. The entiretyof U.S. Pat. No. 8,600,531 is hereby incorporated by reference.

The example signature generator 308 of FIG. 3 stores the generatedsignatures in the example storage device 312 and/or provides thesignatures to the media presentation report generator 314. The examplesignature generator 308 associates (e.g., tags/timestamps) eachgenerated signature with a timestamp indicative of the time and date atwhich the fingerprinted media was received by the sensor interface 306.The signature generator 308 also associates each generated signaturewith an indication of the channel on which the fingerprinted media wasreceived by the sensor interface 306 (e.g., the channel tuned by the STB118, which may be determined by the script interpreter 302 based on thecommands in the script and/or a time at which the script is executed).

In addition or as an alternative to the signature generator 308, theexample watermark extractor 310 of FIG. 3 determines whether anywatermarks or embedded codes are present in the media signals and/ordata. For example, audience measurement systems routinely insert codesinto audio portions of television media. Such codes are mostly orcompletely inaudible (e.g., audio masked) to human listeners but can bedetected by specialized detectors that receive the audio. Examplemethods and apparatus to implement the example watermark extractor 310are described in U.S. Pat. No. 8,369,972. However, any other method ofwatermark extraction or decoding may additionally or alternatively beused. The entirety of U.S. Pat. No. 8,369,972 is hereby incorporated byreference.

If the watermark extractor 310 identifies a watermark in the mediasignals and/or data, the watermark extractor 310 stores the watermark inthe storage device 312 and/or provides the watermark(s) to the mediapresentation report generator 314. The example watermark extractor 310associates (e.g., tags/timestamps) each watermark with a timestampindicative of the time and date at which the watermarked media wasreceived by the sensor interface 306. The watermark extractor 310 alsoassociates each watermark with an indication of the channel presentingthe watermarked media (e.g., the channel tuned by the STB 118, which maybe determined by the script interpreter 302 based on the commands in thescript and/or a time at which the script is executed).

The example media presentation report generator 314 of FIG. 3 generatesand transmits a report to the example clickstream processing system 102of FIG. 1. In the example of FIGS. 1 and 3, the report includes thegenerated signatures and/or the extracted watermarks resulting fromexecuting the script via the media presentation data collector 112 atthe verification site 106. The example report further includestimestamps and channels associated with the signatures and/orwatermarks.

FIG. 4 is pseudocode representative of an example script 400 to collectmedia presentation data and channel information for verifying and/orcorrecting clickstream data. The script 400 represents executableinstructions that may be interpreted and/or executed by, for example,the script interpreter 302 of FIG. 3.

The example script 400 of FIG. 4 performs the following generalfunctions to collect media presentation data and channel information: 1)cause the transmitter interface 304 and/or the remote control 114 ofFIGS. 1 and/or 3 to transmit a command to tune the set top box 118 to adesignated channel using one or more discrete commands; 2) collect mediasignals and/or data; 3) process the collected media signals and/or datato generate signatures and/or extract watermarks; and 4) generate andtransmit a report including the media presentation data and channelinformation when the media presentation data and channel informationhave been collected for each of the channels included in the script 400.

The example script 400 includes a sub-routine 402 to collect and storemedia presentation data and channel information. For example, thesub-routine 402 includes instructions to collect media signals and/ordata (line 406), determine a current time (e.g., to generate atimestamp) (line 408), extract a watermark (line 410), generate asignature (line 412), and store signatures and/or watermarks in thestorage device 312 of FIG. 3 (e.g., in an array) (lines 414-416). In theexample of FIG. 4, lines 414-416 store the signatures and/or watermarksin association with the timestamp and the tuned channel (e.g., avariable representative of a channel). The example “for” loop in line404 of the sub-routine 402 sets a number of loops that may determine aduration of time for which media signals are captured for a particularchannel. In some examples, the duration is received as an input to thesub-routine 402. In some other examples, the duration is a fixedduration set during generation of the script 400.

Line 406 causes the example sensor interface 306 to read media signalsand/or data from the sensor 116 of FIG. 1 (e.g., to “pop” one or moresamples from the sensor 116 from a stack or memory). The example line406 may call another sub-routine associated with a software or firmwaredriver for the sensor 116 to obtain the data. At line 408, the examplescript interpreter 302 stores the current time, which substantiallyrepresents the time at which the media signals were captured via thesensor 116.

Line 410 of FIG. 4 causes the example watermark extractor 310 of FIG. 3to attempt to extract a watermark from the media signals (obtained inline 406). The example line 410 of FIG. 4 calls one or more watermarkextraction sub-routines such as watermark extraction algorithm(s). Insome examples, the watermark extraction algorithm(s) are selected basedon watermarks known (or expected) to be present in the media signals.Line 412 of FIG. 4 causes the example signature generator 308 of FIG. 3to generate one or more signatures of the media signals (obtained inline 406). Line 412 may call another sub-routine such as one or moresignature generation algorithms.

Line 414 stores the generated signature(s) in a data structure such asan array. In the example script 400 of FIG. 4, line 414 stores thesignature(s) in association with the time at which the media signals(from which the signature(s) are generated) were collected and inassociation with the channel to which the set top box 118 was tuned.Similarly, line 416 of FIG. 4 stores any extracted watermark(s) inanother data structure such as an array. Line 416 stores the extractedwatermarks in association with the time at which the media signals (fromwhich the watermarks are extracted) were collected and in associationwith the channel to which the set top box 118 was tuned. The examplesubroutine 402 iterates to store additional media presentation data andchannel information and/or returns to the main body of the script 400,discussed below.

Execution of the example script 400 of FIG. 4 begins at the linedesignated 418, at which the example transmitter interface 304 and/orthe remote control 114 transmit a “1” to the example set top box 118.The set top box 118 is expected to tune to channel 1 in response. Insome examples, the tuning by the set top box 118 is unverified. In someother examples, the clickstream data for the set top box 118 iscollected by the set top box 118. In such examples, the clickstream datamay be obtained from a meter in the set top box 118 and/or requested andreceived from the media provider 104 to confirm (e.g., via theclickstream data verifier 220) that the set top box 118 actually tunedto the channel 1 as intended. In lines 420 and 422, the scriptinterpreter 302 sets an array storage location and a channel variablefor use by the sub-routine 402. The example script interpreter 302 thencalls the example sub-routine 402 at line 424 to collect the mediapresentation data for the tuned channel (e.g., channel 1).

When the sub-routine 402 called at line 424 ends, the script 400continues to lines 426-434 to repeat the tuning of the set top box 118and the collection of media presentation data for channel 10. In theexample lines 426, 428, commanding the set top box 118 to channel 10includes transmitting multiple discrete commands in close succession(e.g., to mimic pushing the “1” button and then, shortly thereafter,pressing the “0” button on a remote control). However, the transmitterinterface 304 and/or the remote control 114 may transmit any number ofdiscrete and/or composite commands to cause the set top box 118 to tuneto the designated channel. Such commands may include navigating a guideand/or incrementing and/or decrementing a channel number (e.g.,mimicking “channel up” and/or “channel down” button presses).

When the sub-routine called at lined 434 ends, an example while loopcauses the script interpreter 302 to wait until a designated time (e.g.,12:05:00 P.M. in the example of FIG. 4). The waiting period may be usedto, for example, avoid having advertisements or other media potentiallyinterfering with subsequent matching of signatures and/or watermarks(e.g., by the clickstream processing system 102 of FIG. 1). When thetime has been reached, at line 438 the transmitter interface 304 and/orthe remote control 114 transmit a ChannelUp signal to cause the set topbox 118 to tune to channel 11 (e.g., after channel 10 from lines 426,428). Line 440 similarly increments the channel variable. Line 442 setsthe array storage location and line 444 calls the sub-routine 402 tocollect the media presentation data for channel 11.

The example tuning, variable assignment, and/or media presentation datacollection repeat for additional channels of interest. When mediapresentation data has been collected for all channels of interest, theexample media presentation report generator 314 generates a new reportdocument or file at line 446. At line 448, the media presentation reportgenerator 314 adds the signature data (e.g., in the signature array) andthe watermark data (e.g., in the watermark array) to the report file.The example media presentation report generator 314 then transmits thereport file to the example clickstream processing system 102 at, forexample, an IP address or domain name of the clickstream processingsystem 102. After transmitting at line 450, the example script 400 ofFIG. 4 ends.

In the example of FIG. 4, the script 400 further includes instructions452-458 to transmit non-tuning commands. Examples of such commandsinclude a volume up command, a volume down command, a mute command, anelectronic guide command, a navigation command (e.g., up, down, left,right commands indicated by directional buttons on a remote control), aconfirmation or selection command (e.g., an “enter” button on a remotecontrol), trick play commands (e.g., pause, play, fast forward, rewind,stop, etc.), and/or any other commands that may be available to a settop box subscribed to the media provider 104 (and/or any otherproviders).

The example non-tuning commands included in the example script 400 maybe used by the clickstream processing system 102 for subsequentverification of clickstream data (e.g., to verify clickstream dataincluding such commands). In some examples, the non-tuning commands areused by the clickstream processing system 102 to infer tuning, such as asequence of clickstream data representative of an electronic guidecommand, a set of navigation (e.g., directional commands to navigate theguide) and/or tuning commands (e.g., numeric commands to navigate theguide), a selection command, and/or an exit command.

While the script 400 explicitly includes channels for clarity ofdescription, the example script 400 may cause the script interpreter 302to refer to a channel information source to determine a next channel tobe tuned. For example, the script interpreter 302 may refer to anelectronic program guide or other resource to determine channels to betuned.

While the example clickstream processing system 102 and the examplemedia presentation data collector 112 of FIGS. 1, 2, and/or 3 aredisclosed above with reference to both signatures and watermarks, eithersignatures or watermarks may be used exclusively (e.g., use onlysignatures). Alternatively, signatures and/or watermarks may be usedpreferentially (e.g., when watermarks can be extracted from the mediasignals, do not generate signatures), or in combination (e.g., generatesignatures and extract watermarks for all or a portion of the data).

FIG. 5A is a table representative of example lineup information 500provided by the example media provider 104 of FIG. 1. The example lineupinformation 500 of FIG. 5 is organized by channel numbers 502-510. Eachof the example channel numbers has a corresponding network/station 512assigned by a multi-channel video programming distributor (e.g., cabletelevision, direct-broadcast satellite, etc.) for the correspondinggeographic area. For example, according to the lineup information 500,the example channel 1 502 for the media provider 104 presents the localaffiliate WABC of national network ABC in the applicable geographicarea.

FIG. 5B is a table representative of example program scheduleinformation 514 provided by the example media provider 104 of FIG. 1.The example program schedule information 514 includes the channels502-510 of FIG. 5A and further specifies time slots 516-522. Using theprogram schedule information 514, the example lineup interpreter 208 ofFIG. 2 determines which media (e.g., Program A 524, Program B 526, etc.)is being presented during a particular time slot or period on aparticular channel number.

When determining what reference data is to be compared to mediapresentation data to verify or correct a channel mapping, the lineupinterpreter 208 of the illustrated example determines the channel502-510 from which the media presentation data was obtained (e.g., whichchannel the verification set top box 118 was tuned to at the time ofcollection) and a time at which the media presentation data wascollected. The example lineup interpreter 208 looks up the time slotcorresponding to the time and channel associated with the mediapresentation data. The lineup interpreter 208 of FIG. 2 provides anidentifier of the media (e.g., an identifier of Program A 524, anidentifier of Program B 526, etc.) to the media data comparator 210.

FIG. 6 is a table representative of a media presentation log 600including media presentation data collected via the example mediapresentation data collector 112 of FIGS. 1 and/or 3. The example mediapresentation log 600 illustrated in FIG. 6 may represent the examplesignature array and/or the example watermark array described withreference to the script 400 of FIG. 4.

The example media presentation log 600 is arranged by channel (e.g.,channel number) 602-610 and by time slots 612-622. Unlike the time slots516-522 of FIG. 5B that are divided into scheduled times, the exampletime slots 612-622 are divided into times during which the mediapresentation data (e.g., watermark data and/or signature data) arecollected. The example time slots 612-622 may therefore be determinedfrom the timestamps associated with the media presentation data.

In the example of FIG. 6, a first watermark 624 was collected (e.g., viathe media presentation data collector 112) between 12:00 P.M. and 12:02P.M. when the set top box 118 of FIG. 1 was tuned to channel 1. A secondwatermark 626 was collected between 12:02 P.M. and 12:04 P.M. while theset top box 118 was tuned to channel 2. Signatures 632 numbered 101-110were generated based on media signals and/or data collected between 1:00P.M. and 1:02 P.M. on channel 1. The limits (e.g., start times and endtimes) of the example time slots 612-622 are determined based on thetimestamps associated with the media presentation data. Thus, one ormore time slots 612-622 may be omitted if no media presentation data iscollected during those time slots.

While each of the example time slots 612-622 illustrated in FIG. 6includes a watermark or signatures, the example time slots may bepopulated with any combination of one or more watermarks, one or moresignatures, and/or any other type of media presentation information. Inthe example of FIG. 6, only one channel 602-610 is populated with mediapresentation data 624-632 for any given time slot 612-622. However, inexamples in which multiple verification sites are used, multiplechannels 602-610 may include media presentation data for a particulartime slot 612-622 and/or two or more time slots 612-622 may overlap.

While an example manner of implementing the clickstream processingsystem 102 of FIG. 1 is illustrated in FIG. 2 and an example manner ofimplementing the media presentation data collector 112 of FIG. 1 isillustrated in FIG. 3, one or more of the elements, processes and/ordevices illustrated in FIGS. 1, 2, and/or 3 may be combined, divided,re-arranged, omitted, eliminated and/or implemented in any other way.Further, the example remote control 114, the example sensor 116, theexample script generator 202, the example channel verifier 204, theexample clickstream media crediter 206, the example lineup interpreter208, the example media data comparator 210, the example watermarkidentifier 212, the example watermark database 214, the examplesignature comparator 216, the example signature database 218, theclickstream data verifier 220, the example script interpreter 302, theexample transmitter interface 304, the example sensor interface 306, theexample signature generator 308, the example watermark extractor 310,the example storage device 312, the example media presentation reportgenerator 314 and/or, more generally, the example clickstream processingsystem 102 and/or the example media presentation data collector 112 ofFIGS. 1, 2, and/or 3 may be implemented by hardware, software, firmwareand/or any combination of hardware, software and/or firmware. Thus, forexample, any of the example remote control 114, the example sensor 116,the example script generator 202, the example channel verifier 204, theexample clickstream media crediter 206, the example lineup interpreter208, the example media data comparator 210, the example watermarkidentifier 212, the example watermark database 214, the examplesignature comparator 216, the example signature database 218, theclickstream data verifier 220, the example script interpreter 302, theexample transmitter interface 304, the example sensor interface 306, theexample signature generator 308, the example watermark extractor 310,the example storage device 312, the example media presentation reportgenerator 314 and/or, more generally, the example clickstream processingsystem 102 and/or the example media presentation data collector 112could be implemented by one or more analog or digital circuit(s), logiccircuits, programmable processor(s), application specific integratedcircuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or fieldprogrammable logic device(s) (FPLD(s)). When reading any of theapparatus or system claims of this patent to cover a purely softwareand/or firmware implementation, at least one of the example remotecontrol 114, the example sensor 116, the example script generator 202,the example channel verifier 204, the example clickstream media crediter206, the example lineup interpreter 208, the example media datacomparator 210, the example watermark identifier 212, the examplewatermark database 214, the example signature comparator 216, theexample signature database 218, the clickstream data verifier 220, theexample script interpreter 302, the example transmitter interface 304,the example sensor interface 306, the example signature generator 308,the example watermark extractor 310, the example storage device 312,and/or the example media presentation report generator 314 is/are herebyexpressly defined to include a tangible computer readable storage deviceor storage disk such as a memory, a digital versatile disk (DVD), acompact disk (CD), a Blu-ray disk, etc. storing the software and/orfirmware. Further still, the example the example clickstream processingsystem 102 and/or the example media presentation data collector 112 ofFIGS. 1, 2, and/or 3 may include one or more elements, processes and/ordevices in addition to, or instead of, those illustrated in FIGS. 1, 2,and/or 3, and/or may include more than one of any or all of theillustrated elements, processes and devices.

Flowcharts representative of example machine readable instructions forimplementing the example clickstream processing system 102 and/or theexample media presentation data collector 112 of FIGS. 1, 2, and/or 3are shown in FIGS. 7, 8, 9A, 9B, and 10. In this example, the machinereadable instructions comprise program(s) for execution by a processorsuch as the processor 1112 shown in the example processor platform 1100discussed below in connection with FIG. 11. The program(s) may beembodied in software stored on a tangible computer readable storagemedium such as a CD-ROM, a floppy disk, a hard drive, a digitalversatile disk (DVD), a Blu-ray disk, or a memory associated with theprocessor 1112, but the entire program(s) and/or parts thereof couldalternatively be executed by a device other than the processor 1112and/or embodied in firmware or dedicated hardware. Further, although theexample program(s) are described with reference to the flowchartsillustrated in FIGS. 7, 8, 9A, 9B, and/or 10, many other methods ofimplementing the example clickstream processing system 102 and/or theexample media presentation data collector 112 may alternatively be used.For example, the order of execution of the blocks may be changed, and/orsome of the blocks described may be changed, eliminated, or combined.

As mentioned above, the example processes of FIGS. 7, 8, 9A, 9B, and/or10 may be implemented using coded instructions (e.g., computer and/ormachine readable instructions) stored on a tangible computer readablestorage medium such as a hard disk drive, a flash memory, a read-onlymemory (ROM), a compact disk (CD), a digital versatile disk (DVD), acache, a random-access memory (RAM) and/or any other storage device orstorage disk in which information is stored for any duration (e.g., forextended time periods, permanently, for brief instances, for temporarilybuffering, and/or for caching of the information). As used herein, theterm tangible computer readable storage medium is expressly defined toinclude any type of computer readable storage device and/or storage diskand to exclude propagating signals and transmission media. As usedherein, “tangible computer readable storage medium” and “tangiblemachine readable storage medium” are used interchangeably. Additionallyor alternatively, the example processes of FIGS. 7, 8, 9A, 9B, and/or 10may be implemented using coded instructions (e.g., computer and/ormachine readable instructions) stored on a non-transitory computerand/or machine readable medium such as a hard disk drive, a flashmemory, a read-only memory, a compact disk, a digital versatile disk, acache, a random-access memory and/or any other storage device or storagedisk in which information is stored for any duration (e.g., for extendedtime periods, permanently, for brief instances, for temporarilybuffering, and/or for caching of the information). As used herein, theterm non-transitory computer readable medium is expressly defined toinclude any type of computer readable storage device and/or storage diskand to exclude propagating signals and transmission media. As usedherein, when the phrase “at least” is used as the transition term in apreamble of a claim, it is open-ended in the same manner as the term“comprising” is open ended.

FIG. 7 is a flowchart representative of example instructions 700 whichmay be executed to implement the example clickstream processing system102 of FIGS. 1 and/or 2 to generate ratings information from clickstreamdata.

The example instructions 700 of FIG. 7 begin by determining (e.g., viathe script generator 202 of FIG. 2) a channel lineup for a mediaprovider (e.g., the media provider 104 of FIG. 1) (block 702). Thechannel lineup may include the set of channels (e.g., channel numbers)that may be tuned by subscribers of the media provider 104. The examplescript generator 202 generates a script for execution by a mediapresentation data collector (e.g., the media presentation data collector112 of FIG. 1) based on the channel lineup (block 704). An examplescript is illustrated and described above with reference to FIG. 4.However, other formats and/or instructions may be used to generate thescript.

The example script generator 202 sends the script to the mediapresentation data collector 112 (block 706). Blocks 702-706 may beperformed during setup and configuration of the media presentation datacollector 112 and/or at any time after setup and/or configuration. Insome examples, the script is provided to the media presentation datacollector 112 at regular intervals. In some other examples, the scriptgenerator 202 only sends an updated script to the media presentationdata collector 112 when the channel lineup has changed (e.g., newchannels have been added and/or channels have been removed from thelineup).

After the script is executed by the media presentation data collector112, the example clickstream processing system 102 (e.g., the channelverifier 204 of FIG. 2) receives media presentation data and channelinformation from the media presentation data collector 112 (block 708).The media presentation data of the illustrated example includeswatermarks, signatures, ID3 tags, and/or other metadata, and timeinformation (e.g., timestamps). The example channel informationrepresents the source(s) of the media from which the media presentationdata (e.g., watermarks and/or signatures) were obtained. The examplechannel information is based on an order of tuning specified in thescript (e.g., the script generated by the script generator 202).

The example clickstream data verifier 220 of FIG. 2 receives theclickstream data associated with the verification site 106 and/or theset top box 118 (block 710). For example, the clickstream data verifier220 receives, from the media provider 104, the clickstream data for theset top box 118 that represents the time period of execution of thescript. The clickstream data is representative of commands to set topboxes (e.g., commands from remote controls controlled by audiencemembers) in associated households. Using the received clickstream dataassociated with the verification site 106 and/or the set top box, theexample clickstream data verifier 220 verifies clickstream commands bycomparing the script to the clickstream data (block 712). For example,the clickstream data verifier 220 may match up timestamps associatedwith data items in the clickstream data to times at which instructionsin the script 400 were to be performed. The times of the instructionsbeing performed may be explicit in the script and/or may be inferredfrom the script.

The example channel verifier 204 verifies and/or corrects channelmappings associated with the media provider 104 based on the mediapresentation data, the channel information, and reference data (block714). For example, the channel verifier 204 may verify that the mediaexpected to be presented on a channel (e.g., channel number) at adesignated time was actually presented on that channel. Exampleinstructions to implement block 714 are disclosed below with referenceto FIG. 8.

When the channel mappings have been verified and/or corrected, theexample clickstream media crediter 206 of FIG. 2 generates verifiedclickstream ratings data and/or crediting by applying the verifiedand/or corrected channel mappings to clickstream data from the mediaprovider 104 (block 716). For example, the clickstream media crediter206 determines a number of set top boxes and/or households that aretuned to a particular channel at a particular time or during a timeslot, identifies the media being presented at the time or during thetime slot using the verified and/or corrected channel mappings, andcredits the identified media with the number of set top boxes and/orhouseholds. The example instructions 700 of FIG. 7 then end and/oriterate to generate clickstream-based ratings data for other areasand/or media providers.

FIG. 8 is a flowchart representative of example instructions which maybe executed to implement the example clickstream processing system 102of FIGS. 1 and/or 2 to verify channel mappings based on collected mediapresentation data. The example instructions 800 of FIG. 8 may beexecuted to implement block 712 of FIG. 7, and are performed afterreceiving media presentation data (e.g., from the media presentationdata collector 112 of FIGS. 1 and/or 3).

The example lineup interpreter 208 of FIG. 2 selects media presentationdata in a media presentation log (block 802). Example media presentationdata includes watermarks 624, 626 and/or signature(s) 632 in the mediapresentation log 600 of FIG. 6. In some other examples, the mediapresentation data may include metadata such as ID3 tags. For purposes ofdiscussion, the example lineup interpreter 208 selects the watermark 624of FIG. 6.

The lineup interpreter 208 determines channel information (e.g., atimestamp and channel) associated with the selected media presentationdata (block 804). For example, the lineup interpreter 208 identifieschannel 1 and the time duration 12:00 P.M. to 12:02 P.M. for thewatermark 624 of FIG. 6. The example media data comparator 210 of FIG. 2identifies reference data corresponding to the determined timestamp(s)and the channel based on the lineup information (block 806). Forexample, the lineup interpreter 208 may identify a watermark and/ormetadata (e.g., an ID3 tag including watermark data) corresponding to anetwork and/or station, and/or may generate a signature representativeof the media (e.g., Program A 524 of FIG. 5B for the 12:00 P.M.-12:02P.M. time slot on channel 1) presented during the identified time rangeand on the identified channel. Based on the media identifier (e.g.,Program A 524), the example media data comparator 210 obtains referencewatermarks (e.g., from the watermark database 214) and/or referencesignatures (e.g., from the signature database 218) that represent themedia identifier.

The example media data comparator 210 determines the network, station,and/or media associated with the selected media presentation data (block808). For example, the watermark identifier 212 of FIG. 2 may determinea media identifier using the watermark 624. In some other examples inwhich the media presentation data includes signature(s), the examplesignature comparator 216 may determine the media identifier by lookingup signature data in the signature database 218.

The example media data comparator 210 determines whether the presentedmedia (identified in block 808) is the same as the reference media(identified in block 806) (block 810). For example, the media datacomparator 210 determines whether a first media identifier determinedbased on the lineup information is the same as a second media identifierdetermined based on the media presentation data obtained from the mediapresentation data collector 112. In some other examples, the media datacomparator 210 may compare reference watermarks and/or referencesignatures determined from the lineup information to watermarks and/orsignatures obtained from the media presentation data collector 112.

If the presented media is the same as the identified reference media(block 810), the example media data comparator 210 confirms that thechannel mapping in the lineup is correct (block 812). For example, themedia data comparator 210 may annotate the lineup information to markthe channel mapping of the media to the times and the channel asverified. On the other hand, if the presented media is not identified asbeing the same as the identified reference media (block 810), theexample media data comparator 210 corrects the lineup information forthe expected channel (e.g., the channel associated with the selectedmedia presentation data) and/or for the channel matching the selectedmedia presentation data (e.g., the channel, network, and/or station thatis actually presenting the media associated with the media presentationdata) (block 814). For example, if Program A (e.g., presented on networkand/or station WABC) is shown in the lineup information as beingpresented on channel 1 but, in fact, is actually presented on channel 2,the example media data comparator 210 identifies which channel presentedProgram A (e.g., channel 2) and/or identifies which network and/orstation (and/or the associated programs) are mapped to channel 1.Example instructions to implement block 814 are disclosed below withreference to FIGS. 9A and 9B.

After confirming that the channel mapping is correct (block 812) orcorrecting the lineup information (block 814), the example channelverifier 204 determines whether there are additional media presentationdata and/or channels to be verified (block 816). If there are additionalmedia presentation data and/or channels to be verified (block 816),control returns to block 802 to select other media presentation datafrom the media presentation log 600. When there are no more mediapresentation data and no more channels to be verified (block 816), theexample instructions 800 of FIG. 8 end, and control returns to block 716of FIG. 7.

FIGS. 9A and 9B illustrate a flowchart representative of exampleinstructions 900 which may be executed to implement the exampleclickstream processing system 102 of FIGS. 1 and/or 2 to correct lineupinformation. The example blocks 902-914 of FIG. 9A may be executed tocorrect lineup information for a channel associated with mediapresentation data (e.g., a channel specified in a script and/orannotated with watermarks and/or signatures obtained from the mediapresentation data collector 112 of FIG. 1). The example blocks 916-928may be executed to correct lineup information for a network and/orstation that is mapped to different channel than indicated in the lineupinformation (e.g., to determine the channel to which a network and/orstation is assigned, different from what is indicated in the lineupinformation). While the example instructions 900 are shown and describedas a process to correct lineup information that includes blocks 902-928,the example blocks 902-914 and the example blocks 916-928 may be splitinto and/or implemented as different processes.

With reference to FIG. 9A, the example instructions 900 begin withselected media presentation data (e.g., selected in block 802 of FIG.8). For clarity of description, the example instructions will bedescribed with reference to the example lineup information 500 of FIG.5A and the example media presentation log 600 of FIG. 6, in which thewatermark 624 is the selected media presentation data and, thus, theassociated channel is channel 1 and the associated timestamp(s) include12:00 P.M. to 12:02 P.M.

The example lineup interpreter 208 and/or the media data comparator 210of FIG. 2 identify reference data for channels, other than the channelassociated with the selected media presentation data (e.g., channel 1),that correspond to the timestamp (e.g., 12:00 P.M. to 12:02 P.M.) forthe selected media presentation data (e.g., watermark 624) based on thelineup information 500 (block 902). For example, the lineup interpreter208 may identify Program B 526, Program E 528, Program I 530, Program K532, and/or other programs on additional channels. The identifiedprograms 526-532 are presented at a same time (e.g., 12:00 P.M.-12:02P.M.) on channels 504-510 different than the channel 502 associated withthe selected media presentation data (e.g., watermark 624). The examplemedia data comparator 210 of FIG. 2 obtains reference data (e.g.,reference signatures, reference watermarks) associated with theidentified programs 526-532 based on, for example, the media identifiersprovided by the lineup interpreter 208.

The example media data comparator 210 selects identified reference datafor one of the other channels (block 904). For example, the media datacomparator 210 selects watermarks and/or signatures associated withProgram B 526. The media data comparator 210 compares the selected mediapresentation data to selected identified reference data (block 906). Forexample, the watermark identifier 212 may determine whether referencewatermarks associated with Program B 526 match watermarks included inthe selected media presentation data. Additionally or alternatively, theexample signature comparator 216 may determine whether signaturesrepresentative of Program B 526 sufficiently match signatures includedin the selected media presentation data.

If the selected media presentation data matches the selected referencedata (block 908), the example channel verifier 204 corrects the lineupinformation (e.g., the lineup information 500) for the channelassociated with the selected media presentation data (block 910). Forexample, the channel verifier 204 changes the lineup information 500 ofFIG. 5A and/or the program schedule 514 of FIG. 5B such thatnetwork/station 512 and/or the Program B 526 and the other programspresented on the same channel as Program B 526 (e.g., Program C, ProgramD, etc.) are associated with the channel 502 of the selected mediapresentation data (e.g., channel 1).

On the other hand, if the selected media presentation data does notmatch the selected reference data (block 908), the example media datacomparator 210 determines whether there is additional reference data(e.g., for additional channels) for comparison to the media presentationdata (block 912). If there is additional reference data for comparison(block 912), control returns to block 904 to select reference datacorresponding to another channel 504-510. If none of the reference datafor the channels 504-510 matches the selected media presentation dataand there are no additional channels (block 912), the example channelverifier 204 annotates or marks the selected media presentation data andthe corresponding channel (e.g., channel 1) for manual identification(block 914). The annotation may prompt a human reviewer to determine achannel, network, and/or station and/or set of programming (e.g., fromthe lineup information and/or from another source).

After correcting the lineup information (block 910) or after annotatingthe selected media presentation data (block 914), the example channelverifier 204 advances to blocks 916-928 of FIG. 9B to correct lineupinformation for a network and/or station, and/or media that is mapped toa different channel than is indicated in the lineup information. Theexample channel verifier 204 obtains reference media data correspondingto the channel (e.g., channel 1) and the time range (e.g., 12:00 P.M. to12:02 P.M.) associated with the selected media presentation data (e.g.,Program A 524) (block 916). For example, the lineup interpreter 208and/or the media data comparator 210 may obtain the reference dataidentified in block 808 of FIG. 8.

The example channel verifier 204 selects media presentation data for achannel (e.g., channel 3 606) different than the expected channel (e.g.,channel 1) during the time range (e.g., 12:00 P.M.-12:30 P.M. time slot)of the media presentation data collection (block 918). For example, themedia data comparator 210 may select the watermark 3 628 associated withchannel 3 and collected between 12:04 P.M. and 12:06 P.M. The media datacomparator 210 (e.g., via the watermark identifier 212 and/or thesignature comparator 216) compares the newly selected media presentationdata (e.g., watermark 3 628) to the reference media data for theexpected channel (e.g., channel 1).

If the newly selected media presentation data (e.g., watermark 3 628)matches reference media data for the expected channel (e.g., channel 1)(block 922), the example channel verifier 204 corrects the lineupinformation for the expected channel (e.g., channel 1) using the newlyselected media presentation data (e.g., watermark 3 628) (block 924).

On the other hand, if the newly selected media presentation data (e.g.,watermark 3 628) does not match the reference media data for theexpected channel (e.g., channel 1) (block 922), the example channelverifier 204 determines whether there is additional collected mediapresentation data (e.g., watermark 4 630) for comparison to thereference media data for the expected channel (e.g., channel 1) (block926). If there is additional collected media presentation data (block926), control returns to block 918 to select next media presentationdata. If none of the collected media presentation data matches thereference media data during the media presentation data collectionperiod (block 922) and there is no more collected media presentationdata for comparison (block 926), the example channel verifier 204annotates or marks the reference media in the lineup information formanual identification of a channel on which the reference media waspresented (block 928).

After correcting the lineup information (block 924) or after annotatingthe reference media (block 928), the example instructions 900 end andcontrol returns to block 816 of FIG. 8. The example instructions 900 maybe executed again in a subsequent iteration of block 814 for differentselected media presentation data.

FIG. 10 is a flowchart representative of example instructions 1000 whichmay be executed to implement the example media presentation datacollector 112 of FIGS. 1 and/or 3 to collect media presentation data.The example instructions 1000 may additionally or alternativelyimplement execution of a script such as the example script 400 of FIG.4.

The example script interpreter 302 of FIG. 3 receipts the script to beexecuted to collect media presentation data (block 1002). The script maybe the example script 400 of FIG. 4 and/or another script generated bythe script generator 202 of FIG. 2 to verify channel lineup informationfor a media provider 104 and/or to credit media presentations withaudiences based on clickstream data. The script interpreter 302determines whether the script is to be executed (block 1004). Forexample, the script 400 may include instructions indicating a time atwhich the script 400 is to be executed. Additionally or alternatively,the script interpreter 302 may be scheduled to execute the script 400 ata predetermined time and/or on a predetermined schedule. If the scriptinterpreter 302 determines that the script 400 is not to be executed(block 1004), the script interpreter 302 loops to block 1004 to waituntil the script 400 is to be executed.

When the script 400 is to be executed (block 1004), the example scriptinterpreter 302 issues command(s) to a set top box (e.g., the set topbox 118 of FIG. 1) via a transmitter (e.g., the remote control 114, thetransmitter interface 304 of FIG. 3) to tune the set top box 118 to achannel based on the script 400 (block 1006). For example, the scriptinterpreter 302 may execute lines 418, lines 426, 428, and/or line 438to cause the transmitter interface 304 and/or the remote control 114 totune the set top box 118 to a channel.

The example sensor interface 306, the example signature generator 308,and/or the watermark extractor 310 collect and/or store mediapresentation data (block 1008). For example, the signature generator 308generates signatures and/or the watermark extractor 310 extractswatermarks from media signals and/or data collected by the sensorinterface 306 of FIG. 3 and/or the sensor 116 of FIG. 1. The signaturegenerator 308 and/or the watermark extractor 310 store the mediapresentation data (e.g., the signature(s) and/or watermark(s)) inassociation with corresponding timestamp(s) (e.g., generated by thesensor interface 306 when collecting the media signals and/or data) andthe channel information (e.g., the channel to which the set top box 118is tuned, determined based on the script) (block 1010). For example, thesignature generator 308 and/or the watermark extractor 310 may store themedia presentation data in the storage device 312 in an array, a logsuch as the media presentation log 600 of FIG. 6, and/or any other datastructure.

The example script interpreter 302 determines whether there areadditional channels to be tuned in the script 400 (block 1012). If thereare additional channels (block 1012), control returns to block 1006 toissue another command to tune the set top box 118 to another channel. Ifthere are no more channels to be tuned (block 1012), the example mediapresentation report generator 314 sends the media presentation data andchannel information collected by executing the script 400 to theclickstream processing system 102 (block 1014). The example mediapresentation data may include, for example, generated signatures and/orextracted watermarks, as well as timestamps of the times at which themedia signals, from which the signatures and watermarks were generated,were collected and the channels the set top box 118 was tuned to at thetime of collection of the media signals. The example instructions 1000may then end. In some examples, the instructions 1000 iterate to collectmedia presentation data in accordance with another script.

FIG. 11 is a block diagram of an example processor platform 1100 capableof executing the instructions of FIGS. 7, 8, 9A, 9B, and/or 10 toimplement the clickstream processing system 102 and/or the mediapresentation data collector 112 of FIGS. 1, 2, and/or 3. The processorplatform 1100 can be, for example, a server, a personal computer, amobile device (e.g., a cell phone, a smart phone, a tablet such as aniPad™), a personal digital assistant (PDA), an Internet appliance, a DVDplayer, a CD player, a digital video recorder, a Blu-ray player, agaming console, a personal video recorder, a set top box, or any othertype of computing device.

The processor platform 1100 of the illustrated example includes aprocessor 1112. The processor 1112 of the illustrated example ishardware. For example, the processor 1112 can be implemented by one ormore integrated circuits, logic circuits, microprocessors or controllersfrom any desired family or manufacturer.

The processor 1112 of the illustrated example includes a local memory1113 (e.g., a cache). The processor 1112 of the illustrated example isin communication with a main memory including a volatile memory 1114 anda non-volatile memory 1116 via a bus 1118. The volatile memory 1114 maybe implemented by Synchronous Dynamic Random Access Memory (SDRAM),Dynamic Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory(RDRAM) and/or any other type of random access memory device. Thenon-volatile memory 1116 may be implemented by flash memory and/or anyother desired type of memory device. Access to the main memory 1114,1116 is controlled by a memory controller.

The processor platform 1100 of the illustrated example also includes aninterface circuit 1120. The interface circuit 1120 may be implemented byany type of interface standard, such as an Ethernet interface, auniversal serial bus (USB), and/or a PCI express interface.

In the illustrated example, one or more input devices 1122 are connectedto the interface circuit 1120. The input device(s) 1122 permit(s) a userto enter data and commands into the processor 1112. The input device(s)can be implemented by, for example, an audio sensor, a microphone, acamera (still or video), a keyboard, a button, a mouse, a touchscreen, atrack-pad, a trackball, isopoint and/or a voice recognition system.

One or more output devices 1124 are also connected to the interfacecircuit 1120 of the illustrated example. The output devices 1124 can beimplemented, for example, by display devices (e.g., a light emittingdiode (LED), an organic light emitting diode (OLED), a liquid crystaldisplay, a cathode ray tube display (CRT), a touchscreen, a tactileoutput device, a light emitting diode (LED), a printer and/or speakers).The interface circuit 1120 of the illustrated example, thus, typicallyincludes a graphics driver card, a graphics driver chip or a graphicsdriver processor.

The interface circuit 1120 of the illustrated example also includes acommunication device such as a transmitter, a receiver, a transceiver, amodem and/or network interface card to facilitate exchange of data withexternal machines (e.g., computing devices of any kind) via a network1126 (e.g., an Ethernet connection, a digital subscriber line (DSL), atelephone line, coaxial cable, a cellular telephone system, etc.).

The processor platform 1100 of the illustrated example also includes oneor more mass storage devices 1128 for storing software and/or data.Examples of such mass storage devices 1128 include floppy disk drives,hard drive disks, compact disk drives, Blu-ray disk drives, RAIDsystems, and digital versatile disk (DVD) drives.

The coded instructions 1132 of FIGS. 7, 8, 9A, 9B, and/or 10 may bestored in the mass storage device 1128, in the volatile memory 1114, inthe non-volatile memory 1116, and/or on a removable tangible computerreadable storage medium such as a CD or DVD.

Although certain example methods, apparatus and articles of manufacturehave been disclosed herein, the scope of coverage of this patent is notlimited thereto. On the contrary, this patent covers all methods,apparatus and articles of manufacture fairly falling within the scope ofthe claims of this patent.

What is claimed is:
 1. An apparatus comprising: a comparator to: comparemedia presentation data representative of media output by a set top boxto reference data associated with first reference media corresponding toa first station to determine whether the media presentation datacorresponds to the reference data, the media presentation data collectedwhile the set top box was tuned to a first channel number; a signaturecomparator to, when the media presentation data does not correspond tothe reference data: identify a plurality of first signatures in adatabase that match a plurality of second signatures included in themedia presentation data, the plurality of first signatures including atleast one of first audio signatures or first video signatures, theplurality of second signatures including at least one of second audiosignatures or second video signatures generated from the media output bythe set top box; determine second reference media corresponding to thefirst signatures; and determine that a second station was scheduled topresent the second reference media at times at which the secondsignatures were generated, wherein the comparator is to relate the firstchannel number to the second station to create a second channel map toreplace a first channel map that relates the first channel number to thefirst station based on channel lineup information for the set top box,the channel lineup information corresponding to a geographic areaassociated with the set top box; and memory to store the mediapresentation data.
 2. The apparatus of claim 1, further including ascript generator to generate a script, the script including instructionsthat, when executed, cause a computing device to issue a sequence ofcommands to the set top box.
 3. The apparatus of claim 2, wherein themedia presentation data includes a first watermark extracted from themedia, the reference data includes a second watermark corresponding tothe first station, and further including a watermark identifier to: lookup the first station in the database based on the first channel map; andobtain the second watermark from the database.
 4. The apparatus of claim3, wherein, when the media presentation data does not correspond to thereference data, the watermark identifier is to: determine a secondchannel number that corresponds to the first station by: comparing thesecond watermark to other watermarks in the media presentation data todetermine a third watermark in the media presentation data that matchesthe second watermark; determining a time at which the third watermarkwas collected from media output by the set top box; and determining thesecond channel number to be a channel to which the set top box was tunedat the time based on the script.
 5. The apparatus of claim 3, whereinthe media presentation data includes an ID3 tag, the ID3 tag includingthe first watermark.
 6. The apparatus of claim 2, wherein the referencedata includes third signatures representative of the first referencemedia, the first reference media is scheduled to be presented on thefirst station according to a program schedule, and the signaturecomparator is to: look up the first station in the database based on thetimes at which the second signatures were generated; and obtain thethird signatures from the database.
 7. The apparatus of claim 6,wherein, when the media presentation data does not correspond to thereference data, the signature comparator is to determine a secondchannel number that corresponds to the first station by: comparing thethird signatures to fourth signatures in the media presentation data,the fourth signatures generated when the set top box was tuned to thesecond channel number; and determining the second channel number to bethe channel to which the set top box was tuned based on the script whenthe fourth signatures were generated.
 8. The apparatus of claim 1,further including a lineup interpreter to identify the first channel mapbased on channel lineup information for the set top box, the channellineup information corresponding to the geographic area associated withthe set top box.
 9. The apparatus of claim 1, wherein the mediapresentation data is generated from audio output from a mediapresentation device, the media presentation device to output the audiobased on the media output by the set top box.
 10. A non-transitorycomputer readable medium comprising instructions which, when executed,cause a processor to at least: compare media presentation datarepresentative of media output by a set top box to reference dataassociated with first reference media corresponding to a first stationto determine whether the media presentation data corresponds to thereference data, the media presentation data collected while the set topbox was tuned to a first channel number; when the media presentationdata does not correspond to the reference data: identify a plurality offirst signatures in a database that match a plurality of secondsignatures included in the media presentation data, the plurality offirst signatures including at least one of first audio signatures orfirst video signatures, the plurality of second signatures including atleast one of second audio signatures or second video signaturesgenerated from the media output by the set top box; determine secondreference media corresponding to the first signatures; and determinethat a second station was scheduled to present the second referencemedia at times at which the second signatures were generated; relate thefirst channel number to the second station to create a second channelmap to replace a first channel map that relates the first channel numberto the first station based on channel lineup information for the set topbox, the channel lineup information corresponding to a geographic areaassociated with the set top box; and store the media presentation data.11. The non-transitory computer readable medium of claim 10, wherein theinstructions cause the processor to generate a script includinginstructions that, when executed, cause a computing device to issue asequence of commands to the set top box.
 12. The non-transitory computerreadable medium of claim 11, wherein the media presentation dataincludes a first watermark extracted from the media, the reference dataincludes a second watermark corresponding to the first station, and theinstructions cause the processor to: look up the first station in thedatabase; and obtain the second watermark from in the database.
 13. Thenon-transitory computer readable medium of claim 12, wherein, when themedia presentation data does not correspond to the reference data, theinstructions cause the processor to: determine a second channel numberthat corresponds to the first station by: comparing the second watermarkto other watermarks in the media presentation data to determine a thirdwatermark that matches the second watermark; determining a time at whichthe third watermark was collected from media output by the set top box;and determining the second channel number to be the channel to which theset top box was tuned at the time based on the script.
 14. Thenon-transitory computer readable medium of claim 12, wherein the mediapresentation data includes an ID3 tag, the ID3 tag including the firstwatermark.
 15. The non-transitory computer readable medium of claim 11,wherein the reference data includes third signatures representative ofthe first reference media, the first reference media is scheduled to bepresented on the first station according to a program schedule, and theinstructions cause the processor to: look up the first station in thedatabase based on the times at which the second signatures weregenerated; and obtain the third signatures from the database.
 16. Thenon-transitory computer readable medium of claim 15, wherein, when themedia presentation data does not correspond to the reference data, theinstructions cause the processor to determine a second channel numberthat corresponds to the first station by: comparing the third signaturesto fourth signatures in the media presentation data, the fourthsignatures generated when the set top box was tuned to the secondchannel number; and determining the second channel number to be thechannel to which the set top box was tuned based on the script when thefourth signatures were generated.
 17. The non-transitory computerreadable medium of claim 10, wherein the instructions cause theprocessor to identify the first channel map based on channel lineupinformation for the set top box, the channel lineup informationcorresponding to the geographic area in which the set top box islocated.
 18. The non-transitory computer readable medium of claim 10,wherein the media presentation data is generated from audio output froma media presentation device, the media presentation device to output theaudio based on the media output by the set top box.
 19. A methodcomprising: comparing, by executing an instruction with a processor,media presentation data representative of media output by a set top boxto reference data associated with first reference media corresponding toa first station to determine whether the media presentation datacorresponds to the reference data, the media presentation data collectedwhile the set top box was tuned to a first channel number; when themedia presentation data does not correspond to the reference data:identifying, by executing an instruction with the processor, a pluralityof first signatures in a database that match a plurality of secondsignatures included in the media presentation data, the plurality offirst signatures including at least one of first audio signatures orfirst video signatures, the plurality of second signatures including atleast one of second audio signatures or second video signaturesgenerated from the media output by the set top box; determining, byexecuting an instruction with the processor, second reference mediacorresponding to the first signatures; and determining, by executing aninstruction with the processor, that a second station was scheduled topresent the second reference media at times at which the secondsignatures w ere generated; relating, by executing an instruction withthe processor, the first channel number to the second station to createa second channel map to replace a first channel map that relates thefirst channel number to the first station based on channel lineupinformation for the set top box. the channel lineup informationcorresponding to a geographic area associated with the set top box; andstoring the media presentation data.
 20. The method of claim 19, furtherincluding generating a script, the script including instructions that,when executed, cause a computing device to issue a sequence of commandsto the set top box.